Camera data management and user interface apparatuses, systems, and methods

ABSTRACT

In certain embodiments, a camera image stored locally by a device is published by the device, over a network, to a content distribution subsystem configured to automatically distribute the camera image to one or more predefined destinations in accordance with a distribution service. The content distribution subsystem automatically distributes the published camera image to the one or more predefined destinations in accordance with the distribution service.

RELATED APPLICATIONS

This application is a divisional application of U.S. patent applicationSer. No. 13/929,942, filed on Jun. 28, 2013, which application is acontinuation application of U.S. patent application Ser. No. 12/165,411,filed on Jun. 30, 2008 and issued on Jul. 2, 2013 as U.S. Pat. No.8,477,228. Both applications are hereby incorporated by reference intheir entirety.

BACKGROUND INFORMATION

As digital picture and data storage technologies have progressed, and asthe costs associated with such technologies have declined, digitalcameras have become commonplace in society. For example, a digitalcamera is included in many mobile phones. However, conventional datamanagement and user interface applications provided with digitalcameras, especially user interface applications provided with cameraphones, tend to be un-intuitive and difficult to use.

BRIEF DESCRIPTION OF THE DRAWINGS

The accompanying drawings illustrate various embodiments and are a partof the specification. The illustrated embodiments are merely examplesand do not limit the scope of the disclosure. Throughout the drawings,identical or similar reference numbers designate identical or similarelements.

FIG. 1 illustrates an exemplary camera data management and userinterface system.

FIG. 2 illustrates an exemplary mobile device having the system of FIG.1 implemented therein.

FIG. 3 illustrates an exemplary session-based organization of cameraimages.

FIGS. 4A-4I illustrate exemplary graphical user interface views that maybe displayed.

FIG. 5 illustrates an exemplary publishing system.

FIG. 6 illustrates an exemplary content distribution subsystem.

FIG. 7 illustrates an exemplary camera data management and userinterface method.

DETAILED DESCRIPTION OF PREFERRED EMBODIMENTS

Exemplary camera data management and user interface apparatuses,systems, and methods are described herein.

In certain exemplary embodiments, a graphical user interface is providedfor display. Various graphical user interface views may be displayed inthe graphical user interface and may be configured to allow a user tointeract with camera related features and functionality, as well ascamera image data. In some examples, a graphical user interfaceincluding a live camera sensor view is displayed and, in response to acapture of a camera image, an image manager pane is displayed togetherwith the live camera sensor view in the graphical user interface. Theimage manager pane includes a visual indicator representative of thecaptured camera image.

In certain exemplary embodiments, a camera image is captured andautomatically assigned to a session based on a predefined sessiongrouping heuristic. Such sessions may be defined and used to organizecamera images and to groups for processing. Examples of sessions andassignment of camera images to sessions are described further below.

In certain exemplary embodiments, data representative of a capturedcamera image is provided to a content distribution subsystem over anetwork, and the content distribution subsystem is configured todistribute data representative of the camera image to a plurality ofpredefined destinations. In some examples, the destinations are definedby a user, and content distribution subsystem is configured to send thecamera image to the defined destinations.

Exemplary embodiments of camera data management and user interfaceapparatuses, systems, and methods will now be described in more detailwith reference to the accompanying drawings.

FIG. 1 illustrates an exemplary camera data management and userinterface system 100 (or simply “system 100”). As shown in FIG. 1,system 100 may include a communication facility 110, processing facility120, storage facility 130, input/output (“I/O”) facility 140, camerafacility 150, session management facility 160, user interface facility170, and publishing facility 180 communicatively connected to oneanother. The facilities 110-180 may be communicatively connected usingany suitable technologies and may communicate using any communicationplatforms and/or technologies suitable for transporting communicationsand data between the facilities 110-180, including well knowncommunication platforms and technologies.

In some examples, system 100 may include any computing hardware and/orinstructions (e.g., software programs), or combinations of computinginstructions and hardware, configured to perform the processes describedherein. In particular, it should be understood that system 100 orcomponents of system 100 may be implemented on one physical computingdevice or may be implemented on more than one physical computing device.Accordingly, system 100 may include any one of a number of well knowncomputing devices, and may employ any of a number of well known computeroperating systems.

One or more of the processes described herein may be implemented atleast in part as computer-executable instructions, i.e., instructionsexecutable by one or more computing devices, tangibly embodied in acomputer-readable medium. In general, a processor (e.g., amicroprocessor) receives instructions, e.g., from a memory, acomputer-readable medium, etc., and executes those instructions, therebyperforming one or more processes, including one or more of the processesdescribed herein. Such instructions may be stored and transmitted usinga variety of known computer-readable media.

A computer-readable medium (also referred to as a processor-readablemedium) includes any medium that participates in providing data (e.g.,instructions) that may be read by a computer (e.g., by a processor of acomputer). Such a medium may take many forms, including, but not limitedto, non-volatile media, volatile media, and transmission media.Non-volatile media may include, for example, optical or magnetic disksand other persistent memory. Volatile media may include, for example,dynamic random access memory (“DRAM”), which typically constitutes amain memory. Transmission media may include, for example, coaxialcables, copper wire and fiber optics, including the wires that comprisea system bus coupled to a processor of a computer. Transmission mediamay include or convey acoustic waves, light waves, and electromagneticemissions, such as those generated during radio frequency (“RF”) andinfrared (“IR”) data communications. Common forms of computer-readablemedia include, for example, a floppy disk, a flexible disk, hard disk,magnetic tape, any other magnetic medium, a CD-ROM, DVD, any otheroptical medium, punch cards, paper tape, any other physical medium withpatterns of holes, a RAM, a PROM, an EPROM, a FLASH-EEPROM, any othermemory chip or cartridge, or any other medium from which a computingdevice can read.

Accordingly, each of the facilities 110-180 may be implemented ashardware, computing instructions (e.g., software) tangibly embodied on acomputer-readable medium, or a combination of hardware and tangiblyembodied computing instructions configured to perform one or more of theprocesses described herein. In certain embodiments, for example, sessionmanagement facility 160, user interface facility 170, and/or one or moreother facilities may be implemented as one or more software applicationsembodied on a computer-readable medium such as storage facility 130 orother memory and configured to direct processing facility 120 to executeone or more of the processes described herein.

The components of system 100 shown in FIG. 1 are illustrative only.Other embodiments may add, omit, or reconfigure one or more components.In certain embodiments, for example, communication facility 110 and/orpublishing facility 180 may be omitted. In certain embodiments, sessionmanagement facility 160 or user interface facility 170 may be omitted.Each of the facilities 110-180 will now be described in more detail.

Communication facility 110 may be configured to send and/or receivecommunications to/from one or more external devices (e.g., a server).Communication facility 110 may include and/or employ any device, logic,communication media, communication protocols, and/or other technologiessuitable for transmitting and receiving communications and data,including data representative of camera images (e.g., photos) and/orpublishing commands and data. Examples of such communicationtechnologies, devices, media, and protocols include, but are not limitedto, data transmission media, communications devices, TransmissionControl Protocol (“TCP”), Internet Protocol (“IP”), File TransferProtocol (“FTP”), Telnet, Hypertext Transfer Protocol (“HTTP”),Hypertext Transfer Protocol Secure (“HTTPS”), Session InitiationProtocol (“SIP”), Simple Object Access Protocol (“SOAP”), ExtensibleMark-up Language (“XML”) and variations thereof, Simple Mail TransferProtocol (“SMTP”), Real-Time Transport Protocol (“RTP”), User DatagramProtocol (“UDP”), Global System for Mobile Communications (“GSM”)technologies, Code Division Multiple Access (“CDMA”) technologies, TimeDivision Multiple Access (“TDMA”) technologies, Short Message Service(“SMS”), Multimedia Message Service (“MMS”), Evolution Data OptimizedProtocol (“EVDO”), radio frequency (“RF”) signaling technologies,signaling system seven (“SS7”) technologies, Ethernet, in-band andout-of-band signaling technologies, and other suitable communicationsnetworks and technologies.

Processing facility 120 may include one or more processors and may beconfigured to execute and/or direct execution of one or more processesor operations described herein. Processing facility 120 may directexecution of operations in accordance with computer-executableinstructions such as may be stored in storage facility 130 or anothercomputer-readable medium. As an example, processing facility 120 may beconfigured to process data, including demodulating, decoding, andparsing acquired data, and encoding and modulating data for transmissionby communication facility 110.

Storage facility 130 may include one or more data storage media,devices, or configurations and may employ any type, form, andcombination of storage media. For example, the storage facility 130 mayinclude, but is not limited to, a hard drive, network drive, flashdrive, magnetic disc, optical disc, random access memory (“RAM”),dynamic RAM (“DRAM”), other non-volatile and/or volatile storage unit,or a combination or sub-combination thereof. Data, including datarepresentative of camera images and/or image metadata, may betemporarily and/or permanently stored in the storage facility 130.

I/O facility 140 may be configured to receive user input and provideuser output and may include any hardware, firmware, software, orcombination thereof supportive of input and output capabilities. Forexample, I/O facility 140 may include one or more devices for capturinguser input, including, but not limited to, a microphone, speechrecognition technologies, keyboard or keypad, touch screen component,receiver (e.g., an RF or infrared receiver), and one or more inputbuttons.

I/O facility 140 may include one or more devices for presenting outputto a user, including, but not limited to, a graphics engine, a display(e.g., a display screen), one or more display drivers, one or more audiospeakers, and one or more audio drivers. Output may include audio,visual, textual, and/or haptic output. In certain embodiments, forexample, I/O facility 140 is configured to display a graphical userinterface (“GUI”) for viewing by a user. Exemplary GUIs that may bedisplayed by I/O facility 140 are described further below.

Camera facility 150 may include any combination of hardware, software,and/or firmware configured to capture camera images. For example, camerafacility 150 may include a still-shot camera, video camera, and/orcomponents of a camera such as a camera lens, camera sensor, etc. Anysuitable camera technologies and devices may be employed. Accordingly,camera facility 150 may capture one or more camera images, includinggenerating data representative of the camera images (e.g., digital imagedata). Data representative of captured images may be provided to one ormore other facilities 110-140 and 160-180 for processing and/or storage.For example, camera image data may be temporarily or permanently storedin storage facility 130. A camera image may include one or more imagesand/or data representative of one or more images captured by camerafacility 150, including, but not limited to, a photograph, video, orother collection of image frames.

Session management facility 160 may be configured to organize, or directprocessing facility 120 to organize, camera images and/or related databy session based on a predefined session grouping heuristic. Sessionmanagement facility 160 may also provide one or more tools for definingsession grouping criteria. Exemplary definitions of session groupingcriteria and session-based organization of camera images are describedfurther below.

User interface facility 170 may be configured to generate, or directprocessing facility 120 to generate, one or more user interfaces. Forexample, one or more GUIs may be generated and provided to I/O facility140 for display. As mentioned, exemplary GUI views are described furtherbelow.

Publishing facility 180 may be configured to execute, or directexecution of, one or more operations for publishing camera images.Publishing may include, but is not limited to, providing one or morecamera images to I/O facility 140 for display, to communication facility110 for transmission to an external device or devices for storage and/ordistribution (e.g., automated predefined distribution), and/or to anexternal service or platform (e.g., a social networking website) fordisplay. Examples of publishing camera images are described furtherbelow.

System 100 may be implemented in a variety of ways and as may suit aparticular application. FIG. 2 illustrates an exemplary mobile device200 having system 100 implemented thereon. Mobile device 200 may includeone or more of the facilities 110-180 shown in FIG. 1 and may beconfigured to perform one or more of the processes and/or operationsdescribed herein. In certain embodiments, mobile device 200 comprises amobile phone device having a built-in digital camera. System 100 may beimplemented in other devices or types of devices in other embodiments.

As shown in FIG. 2, mobile device 200 may include a plurality of inputbuttons 210-1 through 210-8 (collectively “input buttons 210”), whichmay be actuated by a user to provide input to the mobile device 200.Exemplary input buttons may include “soft” and/or “hard” coded inputbuttons. “Soft” coded buttons may be dynamically associated withdifferent user input commands and/or operations based on the context ofoperations of the mobile device 200, and “hard” coded buttons may bestatically associated with corresponding user input commands and/oroperations of the mobile device 200. FIG. 2 illustrates mobile device200 including “soft” input buttons 210-1 and 210-2. Operationsassociated with “soft” input buttons 210-1 and 210-2 may be indicated toa user. FIG. 2 shows a visually indicated “Menu” operation and “Options”operation as being associated with “soft” input buttons 210-1 and 210-2,respectively. Mobile device 200 further includes a “clear” (“CLR”) inputbutton 210-3, a “SEND” input button 210-4, an “END” input button 210-5,a camera mode input button 210-6, a selector button 210-7, and one ormore directional (e.g., “up”, “down,” “left,” and “right”) input buttons210-8.

A user of mobile device 200 may utilize one or more of the input buttons210 to provide user input configured to initiate mobile deviceoperations. For example, camera mode input button 210-6 may be actuatedto activate or terminate operation of a camera mode on mobile device200. When the camera mode is active, camera facility 150 may operate ina state configured for capturing camera images. As another example,directional input buttons 210-8 may be used to navigate a visualselector within a GUI and highlight or otherwise indicate specificselectable items in the GUI. Selector button 210-7 may be used to selectone or more highlighted items and thereby activate one or moreoperations associated with the selected item(s).

As shown in FIG. 2, mobile device 200 may include a display 220configured to display a graphical user interface 230 (“GUI 230”) forviewing by a user of mobile device 200. Display 220 may be included inI/O facility 140 and may include a display screen on which GUI 230 maybe displayed. Examples of GUI 230 and various views that may bedisplayed in GUI 230 are described in detail further below.

To help facilitate an understanding of session management facility 160and session management operations, FIG. 3 illustrates an exemplaryorganization of camera images by session. Camera facility 150 mayacquire camera images 310-1 through 310-N (collectively “camera images310”), and session management facility 160 may organize the acquiredcamera images 310, including selectively organizing the camera images310 into one or more sessions 320-1 through 320-K (collectively“sessions 320”). In certain embodiments, camera images 310 may beautomatically assigned to one or more sessions 320 as the camera images310 are acquired (e.g., as photos are captured).

A session 320 may include a defined grouping of one or more cameraimages 310. A session may be defined as may serve a particularimplementation or application of system 100. In certain embodiments, asession 320 may be defined by specifying one or more criteria to besatisfied to qualify a camera image 310 for inclusion in the session320. When a camera image 310 is determined to satisfy the criteria, thecamera image 310 may be assigned to the session 320.

As an example, a session 320 may be defined as a grouping of one or morecamera images acquired within a continuous time period during which acamera mode is active (i.e., camera facility 150 is in a stateconfigured to acquire camera images). Activation of the camera mode maybe a defined criterion for creating a new session 320, and deactivationof the camera mode may be a defined criterion for closing the session.Accordingly, when a user activates a camera mode, session managementfacility 160 may create a new session 320-1. Any camera images 310-1 and310-2 acquired between the time that the camera mode is activated (andsession 320-1 is created) and the time that the camera mode isdeactivated (and session 320-1 is closed) may be assigned to the session320-1. This process may be repeated for other camera images acquiredduring a period of time between another activation and deactivation ofcamera mode. Camera facility 150 may be configured to activate ordeactivate camera mode in response to predetermined events, such as auser turning camera mode on or off (e.g., using “camera mode” button210-6) or expiration of a predefined length of time since the mostrecent camera image is acquired.

As another example, a session 320 may be defined based on geographiccriteria. For example, a session 320 may be defined to include groupingcriteria specifying a common geographic location (e.g., a particulargeographic position or area). Accordingly, camera images 310 associatedwith the geographic location may be assigned to the session 320. Forinstance, mobile device 200 may be configured to detect the geographiclocation of the mobile device 200, such as by using GPS technologies todetermine GPS coordinates for the detected location of the mobile device200. When a camera image 310 is acquired, location data representativeof the geographic location of the mobile device 200 may be associatedwith the camera image 310. For example, the location data may beincluded in camera image metadata. Session management facility 160 maybe configured to use the location data to selectively assign the cameraimage 310 to the session 320 that has been defined by geographiclocation as described above. Accordingly, camera images 310 associatedwith a particular geographic location (e.g., camera images 310 acquiredwithin the geographic location) may be grouped into a session 320.

As yet another example, a session 320 may be defined based on time data.For example, a session 320 may be defined to include camera images 310associated with (e.g., captured within) a particular time range (e.g., aday, week, month, etc.). Accordingly, camera images 310 may beselectively assigned to sessions 320 based on time data associated withthe camera images 310, such as time data indicating when camera images310 are acquired.

Combinations of various session grouping criteria, including anycombination or sub-combination of the above-described examples ofsession grouping criteria, may be used to define a session 320.

In certain embodiments, session management facility 160 may beconfigured to automatically and selectively assign acquired cameraimages 310 to one or more sessions 320 based on a predefined sessiongrouping heuristic 330. The session grouping heuristic 330 may bedefined to represent one or more defined session grouping criteriaassociated with one or more sessions 320. Accordingly, the sessiongrouping heuristic 330 may include a set of rules configured to be usedby the session management facility 160 to automatically and selectivelyassign acquired camera images 310 to sessions 320.

Session management facility 160 may provide one or more tools configuredto enable a user (e.g., a user of mobile device 200) to manage sessions320, including defining, creating, opening, modifying, closing,deleting, naming, searching, accessing, and otherwise processingsessions 320 or camera images 310 assigned to sessions 320. With thetools, a user of mobile device 200 may custom define one or more sessiongrouping criteria to be satisfied to qualify a camera image 310 to beassigned to a session 320. Session management facility 160 may defineand/or update the session grouping heuristic 330 to represent theuser-defined criteria. Accordingly, a user may create custom sessiongrouping criteria and sessions 320.

In certain embodiments, one or more of the tools provided by sessionmanagement facility 160 may be configured to enable a user to assignidentifiers (e.g., names) to sessions 320. For example, a session 320defined to include camera images 310 associated with a particulargeographic location may be descriptively named. Examples of such sessionnames may include “home,” “work,” “lake,” “road trip,” etc. Sessionmanagement facility 160 may further provide one or more tools forsearching for and selecting sessions 320.

Camera images 310 included in a session 320 may be collectivelydisplayed, identified, selected, and/or processed. As described furtherbelow, user interfaces may display camera images 310 organized bysession 320, or user interfaces may provide an indication of a session320 to which one or more camera images 310 are assigned. A session 320may be selected and the camera images 310 included in the session 320may be collectively selected and processed. For example, a session 320may be selected and published, meaning that the camera images 310 withinthe session 320 are selected and published. Examples of publishing aredescribed further below. Examples of session-based user interface views,session indicators in user interface views, and session-based operationsare described further below.

To help facilitate an understanding of user interface facility 170 andan exemplary user interface provided by user interface facility 170,FIGS. 4A-4I illustrate exemplary GUI views that may be generated andprovided by user interface facility 170 for display.

FIG. 4A illustrates GUI 230 having a live camera sensor view 410displayed therein. Live camera sensor view 410 may be displayed in GUI230 when camera facility 150 is operating in an active camera mode asdescribed above. Live camera sensor view 410 may be a real time or nearreal time representation of a view as detected by a camera sensor.

A camera image (e.g., camera image 310-1) representative of the livecamera sensor view 410 may be captured by camera facility 150. Forexample, a user of mobile device 200 may actuate selector button 210-7or other input mechanism, and camera facility 150 may responsivelycapture a camera image 310-1 representative of the live camera sensorview 410.

When a camera image 310-1 is captured, the view shown in FIG. 4A may beupdated. For example, FIG. 4B illustrates GUI 230 having an imagemanager pane 420 and live camera sensor view 410 displayed togethertherein. In the view shown in FIG. 4B, live camera sensor view 410 maybe as described above and may continue to display a real time or nearreal time representation of a view detected by a camera sensor. In theillustrated example, the image manager pane 420 is displayed as anoverlay of the live camera sensor view 410 of FIG. 4A. This isillustrative only. In other embodiments, the live camera sensor view 410of FIG. 4A may be resized, e.g., adjusted from a full-screen view to apartial screen view, to accommodate the image manager pane 420 in GUI230.

While FIG. 4B illustrates a vertically oriented image manager pane 420positioned along the left side of the live camera sensor view 410 andaligned with the left edge of the GUI 230, this is illustrative only.Other positions, shapes, orientations, and sizes of image manager panes420 may be used in other embodiments. For example, an image manager pane420 may be horizontally oriented and located along a top or bottom edgeof GUI 230. As another example, image manager pane 420 may be configuredto form a border, or a partial border, about the live camera sensor view410 and/or the GUI 230.

Image manager pane 420 may be displayed in GUI 230 in response tocapture of a camera image 310-1 or in response to another predeterminedevent (e.g., a predetermined user input command). In certainembodiments, user interface facility 170 may be configured to continuedisplay of the image manager pane 420 in GUI 230 until an occurrence ofa predetermined event, such as expiration of a predetermined length oftime after capture of camera image 310-1 or deactivation of camera mode.For example, image manager pane 420 may be temporarily displayed whencamera image 310-1 is captured and then hid from view after expirationof a predetermined length of time. When the image manager pane 420 ishid, the view in GUI 230 may return to a full screen live camera sensorview 410 as illustrated in FIG. 4A. In other embodiments, image managerpane 420 may be continued to be displayed in GUI 230 after camera image310-1 is captured and an associated session remains active.

Image manager pane 420 may include one or more visual indicatorsrepresentative of one or more camera images 310. In FIG. 4B, forexample, image manager pane 420 includes visual indicator 440-1, whichis representative of a camera image 310-1 captured from the live camerasensor view 410. Any suitable visual indicator may be employed. Incertain embodiments, visual indicator 440-1 comprises a thumbnail imageof the captured camera image 310-1.

In certain embodiments, visual indicator 440-1 may comprise a selectableobject. FIG. 4B illustrates a selector 450 positioned at (e.g.,highlighting) visual indicator 440-1. A user of mobile device 200 mayprovide input to navigate selector 450 within image manager pane 420 andhighlight and/or select visual indicator 440-1.

One or more operations may be performed on a camera image 310-1associated with a selected visual indicator 440-1 displayed in imagemanager pane 420. For example, with visual indicator 440-1 identified byselector 450, an options button (e.g., “soft” button 210-2) may beactuated. In response, user interface facility 170 may provide a set ofselectable operations that may be applied to the camera image 310-1.Examples of such operations include, but are not limited to, deleting,permanently storing, naming, appending a note to, and publishing thecamera image 310. Examples of such operations being applied to a cameraimage 310-1 or to a group of camera images 310 (e.g., a session 320) aredescribed further below.

With live camera sensor view 410 and image manager pane displayedtogether in GUI 230, a user may view, manage, and operate on cameraimage 310-1 from the image manager pane 420 while also being able toview the live camera sensor view 410. That is, the live camera sensorview 410 does not have to be closed from view in order for a user toview, manage, or operate on captured camera image 310-1.

In certain examples, another camera image 310-2 may be captured from theuser interface view illustrated in FIG. 4B. For example, while the viewshown in FIG. 4B is displayed in GUI 230, a user of mobile device 200may actuate selector button 210-7 or other input mechanism, and camerafacility 150 may responsively capture another camera image 310-2representative of the live camera sensor view 410.

When the other camera image 310-2 is captured, the view shown in FIG. 4Bmay be updated. For example, FIG. 4C illustrates GUI 230 having visualindicators 440-1 and 440-2 (collectively “visual indicators 440”)included in the image manager pane 420. Visual indicator 440-2 may beadded to the image manager pane 420 and may represent the newly capturedcamera image 310-2.

In FIG. 4C, selector 450 is positioned at visual indicator 440-2. Incertain embodiments, user interface facility 170 may be configured toautomatically position selector 450 at the most recently added visualindicator 440-2 in image manager pane 420. In the present example, forinstance, selector 450 is repositioned from visual indicator 440-1 inFIG. 4B to visual indicator in FIG. 4C when camera image 310-2 iscaptured and visual indicator 440-2 added to image manager pane 420.

Selector 450 may be navigated within the image manager pane 420 inaccordance with user input. For example, actuation of an “up”directional button 210-8 may cause selector 450 to move from visualindicator 440-2 to visual indicator 440-1 in FIG. 4C. Accordingly, auser may navigate selector 450 within image manager pane 420 and selectand initiate operation on any camera image 310 associated with a visualindicator 440 included in the image manager pane 420.

In certain embodiments, when live camera sensor view 410 and imagemanager pane 420 are displayed together in GUI 230, certain inputs maybe defined as being associated with either live camera sensor view 410or image manager pane 420. For example, when the view shown in FIG. 4Cis displayed in GUI 230, actuation of a certain one of the input buttons210 of mobile device 200 may be configured to initiate capture of acamera image 310, while actuation of one or more of the other inputbuttons 210 of mobile device 200 may be configured to initiatenavigating between and selecting visual indicators 440 included in theimage manager pane 420. Accordingly, the live camera sensor view 410 andthe image manager pane 420 may be concurrently active for receivingcertain user input and performing corresponding operations.

In other embodiments, user interface facility 170 may be configured totoggle an active input mode between the live camera sensor view 410 andthe image manager pane 420 in response to user input. When the livecamera sensor view 410 or the image manager pane 420 is in active inputmode, user input may be received for the particular view 410 or pane420. As an example of toggling input mode, when input mode is active inimage manager pane 420, receipt of predetermined user input may causeinput mode to become inactive for image manager pane 420 and active forthe live camera sensor view 410. In certain examples, the “right”directional input button 210-8 may be associated with switching activeinput mode from the image manager pane 420 to the live camera sensorview 410. A visual indication of a toggle active input mode command maybe displayed in GUI 230. FIGS. 4B and 4C each illustrate a visual“right” directional arrow indicator 455-1 positioned adjacent toselector 450 and pointing in the direction of the live camera sensorview 410. This may indicate that actuation of the “right” directionalinput button 210-8 may be configured to cause active input mode toswitch from the image manager pane 420 to the live camera sensor view410. Similarly, another predetermined input, such as the “left directioninput button 210-8, for example, may be configured to cause active inputmode to switch from the live camera sensor view 410 to the image managerpane 420.

In certain embodiments, image manager pane 420 may be session specific.That is, visual indicators 440 in image manager pane 420 may beassociated with camera images 310 corresponding to a particular session320. As an example, when a camera image 310-2 is captured and assignedto a session 320-1, user interface facility 170 may be configured toinclude in image manager pane 420 content associated with the samesession 320-1. For example, visual indicators 440-1 and 440-2 may beincluded in image manager pane 420 at least because the respectivelycorresponding camera images 310-1 and 310-2 are associated with the samesession 320-1. A session 320-1 to which the most recently acquiredcamera images are assigned may be referred to as an “active session,”and the image manager pane 420 may be configured to include visualindicators 440 of the camera images associated with an active session.

An image manager pane 420 having session specific content may helpreduce the chance for confusion and/or error as compared to conventionalcamera interfaces that are not session specific. For example, whencamera images 310-1 and 310-2 are captured and assigned to a session320-1 and visual indicators 440-1 and 440-2 associated with capturedcamera images 310-1 and 310-2 are displayed in the image manager pane420, the user may be able to manage the camera images 320-1 and 320-2 inthe session 320-1 individually or as a group without having to considerother camera images not associated with the session 320-1. For instance,without having to view and/or sort through other camera images notincluded in the session 320-1, a user may scroll through visualindicators 440-1 and 440-2 in the image manager pane 420 and initiateperformance of operations on at least one of the corresponding cameraimages 310-1 and 310-2, such as deleting an unwanted camera image (e.g.,camera image 310-2) from the session 320-1 before permanently saving theremaining camera image (e.g., camera image 310-1) in storage facility130.

User interface facility 170 may be configured to provide othersession-specific views and/or session indicators associated with cameraimages 310. As an example, FIG. 4D illustrates an exemplary cameraimages library view 460 in GUI 230. As shown, the library view 460 mayinclude a plurality of visual indicators 440-1 through 440-J, each ofwhich may correspond with a camera image 310. GUI 230 may furtherinclude session indicators 470-1 through 470-2 (collectively “sessionindicators 470”) configured to indicate that particular visualindicators 440-1 through 440-2 and/or corresponding camera images (e.g.,camera images 310-1 and 310-2) are associated with a common session320-1. Accordingly, a user may discern from a GUI view which cameraimages 310-1 and 310-2 are associated with a particular session 320-1.While FIG. 4D illustrates exemplary session indicators 470, othersession indicators or types of session indicators may be used in otherembodiments. For example, similar colors, backgrounds, borders,brightness, or opacity may be used to indicate association with a commonsession 320-1.

User interface facility 170 may be configured to provide a user with acapability to select multiple visual indicators 440 from those includedin image manager pane 420 or library view 460. For example, selector 450may be used to navigate and select one or more visual indicators 440-1and 440-4 to create a group of selected camera images (camera images310-1 and 310-4 associated with visual indicators 440-1 and 440-4).

In certain embodiments, user interface facility 170 may be configured toenable a user to navigate to and select a particular visual indicator440-1 or corresponding camera image 310-1 associated with a session320-1, and from the selected visual indicator 440-1 or camera image310-1, choose to select all other camera images (e.g., camera image310-2 corresponding with visual indicator 440-2) that are associatedwith the same session 320-1. As an example, with visual indicator 440-1highlighted by selector 450 as shown in FIG. 4D, a user may select an“options” input button (e.g., “soft” input button 210-2) to launch awindow in GUI 230 including selectable operations that may be performedin relation to the camera image 310-1 associated with visual indicator440-1.

FIG. 4E illustrates an exemplary options window 475-1 displayed in GUI230. Options window 475-1 may include one or more selectable optionsassociated with one or more operations that may be applied to theselected visual indicator 440-1 and/or corresponding camera image 310-1.Examples of such options and/or operations may include deleting,editing, zooming in on, and publishing the selected camera image 310-1.As shown, one of the selectable options in options window 475-1 maycorrespond with an operation for identifying and selecting all cameraimages associated with the same session 320-1 as the selected cameraimage 310-1. When this option is selected, all camera images 310associated with session 320-1 are selected for inclusion in a selectedgroup.

The selected group may be indicated in GUI 230. FIG. 4F illustrateslibrary view 460 with multiple visual indicators 440-1 and 440-2visually marked to represent inclusion of the corresponding cameraimages 310-1 and 310-2 in a user-selected group. In the illustratedexample, group indicators comprise checkmark graphics associated withvisual indicators 440-1 and 440-2. This is illustrative only. Othergroup indicators may be used in other embodiments.

Camera images 310-1 and 310-2 selected for inclusion in a group may beoperated on as a group. With a group of camera images 310-1 and 310-2selected as shown in FIG. 4F, for example, a user may select an“options” input (e.g., “soft” input button 210-2) to launch anotheroptions window 475-2 in GUI 230 including selectable operations that maybe applied to the selected group of camera images 310-1 and 310-2. FIG.4G illustrates another options window 475-2 including selectableoperations for editing, deleting, and published camera images 310-1 and310-2 as a group. If one of the selectable options in options window475-2 is selected, one or more operation(s) associated with the selectedoption will be applied to the selected group of camera images 310. As anexample, camera images 310-1 and 310-2 included in a selected group maybe published concurrently when a user selects a “publishing” option fromthe options window 475-2 shown in FIG. 4G.

While any of a number of operations may be applied to a selected cameraimage 310 or selected group of camera images 310, examples of publishingone or more selected camera mages 310 will now be described. Publicationof a camera image 310 or group of camera images 310 may include, but isnot limited to, sending one or more camera images 310 to another device(e.g., another mobile phone), to a contact in a contacts database, to anexternal service or site (e.g., a social networking site), to adistribution server, to storage facility 130, to an external datastorage facility, to I/O facility 140 for display, and to any otherfacility of or interface to system 100.

As an example, a user may wish to send a selected group of camera images310-1 and 310-2 to a person included in a contacts database. In the viewshown in FIG. 4G, the user may select the “Publish Images” option fromthe options window 475-2. In response to this selection, another optionswindow 475-3 may be displayed in GUI 230, such as is illustrated in FIG.4H. Options window 475-3 may include selectable options for publishingthe selected camera images 310-1 and 310-2. In the example shown in FIG.4H, the selectable options include options for publishing the selectedcamera images 310-1 and 310-2 to a social network site, to a weblocation (e.g., a particular website), to one or more contacts, to alocally defined distribution list (e.g., a predefined group ofcontacts), and to an distribution service labeled “Express.” Examples ofpublishing to an exemplary distribution service are described furtherbelow.

If the user selects the “Contacts” option from the list of options inoptions window 475-3, user interface facility 170 may display anotheroptions window 475-4 in GUI 230, such as is illustrated in FIG. 4I. Asshown in FIG. 4I, options window 475-4 may include one or moreselectable options corresponding with predefined contacts, which may beaccessed from a contacts database stored in storage facility 130. A usermay select one of the contacts listed in options window 475-4. Inresponse, publishing facility 180 may initiate transmission of datarepresentative of the selected camera images 310-1 and 310-2 to one ormore communication devices associated with the selected contact in thecontacts database. For example, the data may be transmitted to a mobilephone, e-mail address, and/or other destination specified in thecontacts database.

Sending camera images 310 to a selected contact is just one example ofpublishing camera images 310. As mentioned above, publishing may includeproviding data representative of camera images 310 to other destinationssuch as a website and/or a social networking site (e.g., a user's pageon a social networking site).

Another example of publishing camera images 310 includes sending acamera image or selected group of camera images to a distributionservice for distribution of the camera image or selected group of cameraimages by the service to one or more predefined destinations. FIG. 5illustrates an exemplary publishing system 500 (or simply “system 500”)in which mobile device 200 may provide (e.g., upload) one or more cameraimages 310 to a content distribution subsystem 510 over a network 525.Content distribution subsystem 510 may be configured to distribute thecamera images 310 to one or more predefined destinations 530. FIG. 5shows a single camera image 310-1 being uploaded from mobile device 200to content distribution subsystem 510 and distributed from contentdistribution subsystem 510 to a plurality of predefined destinations530.

Mobile device 200 and content distribution subsystem 510 may communicateover network 525 using any communication platforms and technologiessuitable for transporting data and/or communication signals, includingknown communication technologies, devices, media, and protocolssupportive of remote data communications, examples of which include, butare not limited to, data transmission media, communications devices,Transmission Control Protocol (“TCP”), Internet Protocol (“IP”), FileTransfer Protocol (“FTP”), Telnet, Hypertext Transfer Protocol (“HTTP”),Hypertext Transfer Protocol Secure (“HTTPS”), Session InitiationProtocol (“SIP”), Simple Object Access Protocol (“SOAP”), ExtensibleMark-up Language (“XML”) and variations thereof, Simple Mail TransferProtocol (“SMTP”), Real-Time Transport Protocol (“RTP”), User DatagramProtocol (“UDP”), Global System for Mobile Communications (“GSM”)technologies, Code Division Multiple Access (“CDMA”) technologies,Evolution Data Optimized Protocol (“EVDO”), Time Division MultipleAccess (“TDMA”) technologies, Short Message Service (“SMS”), MultimediaMessage Service (“MMS”), radio frequency (“RF”) signaling technologies,wireless communication technologies (e.g., Bluetooth, Wi-Fi, etc.),in-band and out-of-band signaling technologies, and other suitablecommunications networks and technologies.

Network 525 may include one or more networks, including, but not limitedto, wireless networks, mobile telephone networks (e.g., cellulartelephone networks), closed media networks, open media networks, closedcommunication networks, open communication networks, satellite networks,navigation networks, broadband networks, narrowband networks, voicecommunications networks (e.g., VoIP networks), the Internet, wide areanetworks, local area networks, public networks, private networks, andany other networks capable of carrying data and/or communicationssignals between mobile device 200 and content distribution subsystem510. In certain exemplary embodiments, network 525 includes a mobiletelephone network, and content distribution subsystem 510 and mobiledevice 200 are configured to communicate with one another using mobilephone network communication technologies.

In some examples, system 500 may include any computing hardware and/orinstructions (e.g., software programs), or combinations of computinginstructions and hardware, configured to perform the processes describedherein. In particular, it should be understood that components of system500 may be implemented on one physical computing device or may beimplemented on more than one physical computing device. Accordingly,system 500 may include any one of a number of computing devices and/orcomputer operating systems (e.g., mobile device operating systems).

Accordingly, the processes described herein may be implemented at leastin part as computer-executable instructions, i.e., instructionsexecutable by one or more computing devices, tangibly embodied in acomputer-readable medium. In general, a processor (e.g., amicroprocessor) receives instructions, e.g., from a memory, acomputer-readable medium, etc., and executes those instructions, therebyperforming one or more processes, including one or more of the processesdescribed herein. Such instructions may be stored and transmitted usinga variety of known computer-readable media, including anycomputer-readable medium described above.

Predefined destinations 530 may include any device, service, or otherdestination configured to receive camera images 310 distributed bycontent distribution subsystem 510. Examples of predefined destinations,include, but are not limited to, another device associated with a userof mobile device 200 (e.g., a personal computer or television serviceset-top box), another mobile device 200 associated with the user oranother user (e.g., another mobile phone), a server device associatedwith a service (e.g., a social networking site server), a data storagedevice and/or service, and any other destination configured to receivedistributed data representative of camera images 310.

Any suitable communications technologies may be used to distributecamera images 310 from content distribution subsystem 510 to one or morepredefined destinations 530, including any of the communicationsdevices, protocols, formats, networks, and technologies described above.Content distribution subsystem 510 may be configured to distributecamera images 310 over the same network 525 used for communications withmobile device 200 (“in network”) and/or over communication channelscontrolled by a common franchise (“in franchise”). Alternatively oradditionally, content distribution subsystem 510 may be configured todistribute camera images 310 over communications channels other thanthose used for communications with mobile device 200 (“out of network”)and/or communication channels other than those controlled by a commonfranchise (“out of franchise”).

Distribution of camera images 310 by content distribution subsystem 510may allow a user of mobile device 200 to minimize or avoid fees that maynormally be charged for sending data representative of camera images310. For example, certain conventional mobile phone services may bestructured to charge a fee for each such communication sent from mobiledevice 200. Accordingly, if a user of mobile device 200 sent cameraimages 310 directly from the mobile device 200 to multiple predefineddestinations 530, a fee may be incurred for each separate communication.Alternatively, the user of the mobile device 200 may send the cameraimages 310 to content distribution subsystem 510 and incur only a feefor this transmission. The content distribution subsystem 510 maydistribute the camera images 310 to multiple predefined destinations 530without the user of the mobile device 200 incurring additional fees forthe distribution.

Content distribution subsystem 510 may comprise one or more devices(e.g., one or more servers) configured to receive and distribute datarepresentative of camera images 310 using one or more communicationtechnologies. FIG. 6 illustrates an exemplary content distributionsubsystem 510. The components of content distribution subsystem 510 mayinclude or be implemented as hardware, computing instructions (e.g.,software) embodied on one or more computer-readable media, or acombination thereof. In certain embodiments, for example, one or morecomponents of content distribution subsystem 510 may include or beimplemented on at least one server configured to communicate overnetwork 525. While an exemplary content distribution subsystem 510 isshown in FIG. 6, the exemplary components illustrated in FIG. 6 are notintended to be limiting. Indeed, additional or alternative componentsand/or implementations may be used.

As shown in FIG. 6, content distribution subsystem 510 may include acommunication module 610, which may be configured to communicate withmobile device 200, including receiving data representative of cameraimages 310 from mobile device 200 and providing data representative ofcamera images 310 to one or more predefined destinations 530.Communication module 610 may be configured to support a variety ofcommunication platforms, protocols, and formats such that contentdistribution subsystem 510 can receive content from and distributecontent to a variety of computing platforms (e.g., a mobile telephoneservice platform, a web-based platform, a subscriber televisionplatform, etc.) and using a variety of communications technologies.Accordingly, the content distribution subsystem 510 can support amulti-platform system in which content can be received from and providedto diverse platforms.

Content distribution subsystem 510 may include a processing module 620configured to control operations of components of the contentdistribution subsystem 510. Processing module 620 may execute or directexecution of operations in accordance with computer-executableinstructions stored to a computer-readable medium such as a data store630. As an example, processing module 620 may be configured to process(e.g., encode, decode, modulate, and/or demodulate) data andcommunications received from or to be transmitted to mobile device 200and/or predefined destinations 530. As another example, processingmodule 620 may be configured to perform data management operations ondata stored in data store 630. For example, processing module 620 mayoperate on data, including storing data to data store 630 and indexing,searching, accessing, retrieving, modifying, annotating, copying, and/ordeleting data stored in data store 630.

Data store 630 may include one or more data storage media, devices, orconfigurations and may employ any type, form, and combination of storagemedia. For example, the data store 630 may include, but is not limitedto, a hard drive, network drive, flash drive, magnetic disc, opticaldisc, random access memory (“RAM”), dynamic RAM (“DRAM”), othernon-volatile and/or volatile storage unit, or a combination orsub-combination thereof. Data store 630 may store any suitable type orform of electronic data, including camera image data 640 and profiledata 650.

Camera image data 640 may include data representative of one or morecamera images 310, including camera images 310 received from mobiledevice 200 over network 525. Camera image data 640 may further includedata related to camera images 310, including camera image metadata, forexample.

Profile data 650 may include information associated with one or moreusers, which may include subscribers to one or more services providedover network 525, such as a user of mobile device 200. Profile data 650may include any information descriptive of the users, user preferences,user-specific settings, and/or services provided to the users. Incertain embodiments, profile data 650 may include predefineddistribution settings associated with users. The predefined distributionsettings may be used to identify one or more destinations to whichcamera images 310 will be distributed, as described further below.

Distribution settings for a user may be custom defined by the user.Content distribution subsystem 510 and/or mobile device 200 may beconfigured to provide one or more tools for custom definition ofdistribution settings. The tools may be provided in any suitable way andmay include any mechanisms or processes that a user may utilize tocustom define one or more predefined distribution destinations 530. Forexample, a graphical user interface may be provided and may include oneor more tools configured to enable a user to provide distributioninformation and settings. Accordingly, a user profile may includepersonalized distribution settings specifying one or more predefineddistribution destinations and related information such as addresses,access information (e.g., user name and password), interface information(API access information), and any other information potentially helpfulfor identifying distribution destinations and distributing camera images310 thereto. Accordingly, a user profile and predefined distributionsettings included therein may be used to automatically distribute datarepresentative of camera images 310 from content distribution subsystem510 to one or more predefined destinations 530.

As shown in FIG. 6, content distribution subsystem 510 may furtherinclude a distribution module 660, which may include or be implementedas hardware, computing instructions (e.g., software) tangibly embodiedon a computer-readable medium, or a combination of hardware and embodiedcomputing instructions configured to perform one or more of the contentdistribution processes described herein. In certain embodiments,distribution module 660 may be implemented as a software applicationembodied on a computer-readable medium such as data store 630 andconfigured to direct the processing module 620 to execute one or more ofthe processes described herein.

Content distribution subsystem 510 may be configured to recognize whenone or more camera images 310 received from mobile device 200 are to bedistributed based on predefined distribution settings specified in userprofile data 650. Content distribution subsystem 510 may identify one ormore predefined distribution destinations from the predefineddistribution settings and may distribute, or initiate distribution of,the camera images 310 to the predefined destinations 530.

As an example, when a user of mobile device 200 selects the “ExpressDistribution Service” option from the list of selectable options inoptions window 475-3 shown in FIG. 4H, mobile device 200 may providedata representative of a selected camera image 310-1 (or selected groupof camera images 310 in other examples) to content distributionsubsystem 510 over network 525 as illustrated in FIG. 5. Along with thecamera image 310-1, mobile device 200 may provide an indication that thecamera image 310-1 is provided for distribution in accordance with anexpress distribution service. Communication module 610 may receive thedata, and distribution module 660 may recognize from the data a requestfor distribution of the camera image 310-1 in accordance with theexpress distribution service. Distribution module 660 may access anappropriate profile in the profile data 650, such as a profileassociated with the user of mobile device 200 from which the cameraimage 310-1 is received. Distribution module 660 may use predefineddistribution settings specified in the identified profile to determineone or more predefined destinations 530 to which camera image 310-1 willbe sent. Using information included in the distribution settings,distribution module 660 may initiate distribution of camera image 310-1to the identified predefined destinations 530. The camera image 310-1may be automatically distributed to the predefined destinations 530 inaccordance with the predefined distribution settings and without humanintervention. In this or similar manner, a user may upload one or morecamera images 310 from mobile device 200 to content distributionsubsystem 510 for automatic distribution from the content distributionsubsystem 510 to one or more predefined destinations 530. Accordingly,acquired camera images 310 may be managed including by being uploadedand automatically sent to predefined destinations 530 such as a blog, adata backup storage facility, and/or a social networking site.

User interface facility 170 may be configured to provide visualanimation effects in GUI 230 in association with one or more of the GUIviews and/or one or more of the operations described above. For example,animation effects may be displayed and may be representative oftransfer, capture, and/or publishing of camera images 310. In certainembodiments, animation effects may be displayed concurrently withperformance of data transfer, capture, and/or publishing operations.Animation effects may help improve a user experience during memoryaccess delay periods.

As an example of animation effects, when the GUI view shown in FIG. 4Bis displayed and a user captures a camera image 310-2, user interfacefacility 170 may provide animation effects designed to animate a captureof the camera image 310-2 and/or a data transfer of the camera image310-2 from live camera sensor view 410 to image manager pane 420. Incertain embodiments, the animation effects may be designed to illustratea funnel flow of camera image pixels, such as from the live camerasensor view 410 to visual indicator 440-2 in the image manager pane 420.In other embodiments, the animation effects may be designed toillustrate a spiral flow and/or compression of camera image pixels, suchas from the live camera sensor view 410 to visual indicator 440-2 in theimage manager pane 420. Such animation effects may provide a visualappearance of pixels being sucked into visual indicator 440-2 from thelive camera sensor view 410. These examples are illustrative only andmay be used in other GUI views, including visually indicator capture andstorage of a camera image 310-2 to library view 460. Other animationeffects may be used in other embodiments.

As another example, animation effects may be provided and configured toanimate publishing of camera images 310. For example, animation effectsmay illustrate an expansion of pixels and/or a flow of pixels from avisual indicator 440-2 to a publishing destination 530 such as to adisplay of a full screen view of a camera image 310-2 and/or transportof pixels to an external destination such as a social networking site.

FIG. 7 illustrates an exemplary camera data management and userinterface method. While FIG. 7 illustrates exemplary steps according toone embodiment, other embodiments may omit, add to, reorder, and/ormodify any of the steps shown in FIG. 7.

In step 710, a camera image is acquired. Step 710 may be performed inany of the ways described above, including camera facility 150 capturingthe camera image.

In step 720, the acquired camera image is assigned to at least onesession based on a predefined session grouping heuristic. Step 720 maybe performed in any of the ways described above, including using one ormore criteria in the predefined session grouping heuristic 330 todetermine that the camera image qualifies for assignment to the session.Step 720 may be performed automatically.

In step 730, a graphical user interface is provided for display. Step730 may be performed in any of the ways described above, including userinterface facility 170 generating and providing graphical user interface230 to I/O facility 140, which may display the graphical user interface230 for viewing by a user.

As described above, various graphical user interface views may bedisplayed in graphical user interface 230, including any of theexemplary graphical user interface views described above and/orillustrated in the accompanying drawings. User input may be received anduser output may be provided by way of the graphical user interfaceviews, as described above. As an example, in step 740, animation effectsrepresentative of acquisition of the camera image may be provided ingraphical user interface in any of the ways described above.

In step 750, a group of one or more camera images may be identifiedbased on user input. Step 750 may be performed in any of the waysdescribed above, including a user navigating and selecting one or morevisual indicators representative of the one or more camera images ingraphical user interface 230. From the user selections, user interfacefacility 170 may identify the group of one or more selected cameraimages.

In step 760, the group of one or more selected camera images ispublished. Step 760 may be performed in any of the ways described above,including recognizing a publishing command provided by a user (e.g., byselecting a “publishing” option in graphical user interface 230) andproviding data representative of the one or more selected camera images.In certain embodiments, publishing may include sending datarepresentative of the one or more selected camera images to contentdistribution subsystem 510 over network 525.

In step 770, data representative of the one or more selected cameraimages is distributed to one or more predefined destinations. Step 770may be performed in any of the ways described above, including contentdistribution subsystem 510 receiving data representative of the one ormore camera images and automatically distributing data representative ofthe one or more camera images to one or more predefined destinations. Incertain embodiments, the camera images are distributed to the predefineddestinations in accordance with distribution settings included in aprofile (e.g., a user profile).

In the preceding description, various exemplary embodiments have beendescribed with reference to the accompanying drawings. It will, however,be evident that various modifications and changes may be made thereto,and additional embodiments may be implemented, without departing fromthe scope of the invention as set forth in the claims that follow. Forexample, certain features of one embodiment described herein may becombined with or substituted for features of another embodimentdescribed herein. The description and drawings are accordingly to beregarded in an illustrative rather than a restrictive sense.

What is claimed is:
 1. A method comprising: capturing, by a mobiledevice, a plurality of camera images; locally storing, by the mobiledevice, the plurality of camera images; automatically assigning, by themobile device, a camera image included in the plurality of camera imagesto a session based on the camera image being captured during aparticular time range; providing, by the mobile device for display on adisplay screen of the mobile device, a session specific image managerpane together with a live camera sensor view in a graphical userinterface, the session specific image manager pane including datarepresentative of camera images assigned to the session; receiving, bythe mobile device, user input requesting that the data representative ofthe camera image assigned to the session be published, over a network,to a content distribution subsystem for automatic distribution by thecontent distribution subsystem to one or more predefined destinations inaccordance with a distribution service; and in response to the receivingof the user input request, uploading, by the mobile device, the datarepresentative of the camera image assigned to the session, over thenetwork, to the content distribution subsystem, and providing, by themobile device, an indication, over the network, that the datarepresentative of the camera image assigned to the session is providedfor automatic distribution by the content distribution subsystem to theone or more predefined destinations in accordance with the distributionservice.
 2. The method of claim 1, wherein the one or more predefineddestinations comprises a data backup storage device remote from themobile device.
 3. The method of claim 2, wherein the one or morepredefined destinations further comprises at least one of: a computingdevice remote from the mobile device and associated with a user of themobile device; and another mobile device associated with another user.4. The method of claim 1, further comprising: receiving, by the contentdistribution subsystem, the data representative of the camera imageassigned to the session and the indication that the data representativeof the camera image assigned to the session is provided for automaticdistribution by the content distribution subsystem to the one or morepredefined destinations in accordance with the distribution service; andautomatically distributing, by the content distribution subsystem inresponse to the receiving of the data representative of the camera imageassigned to the session and the indication that the data representativeof the camera image assigned to the session is provided for automaticdistribution by the content distribution subsystem to the one or morepredefined destinations in accordance with the distribution service, thedata representative of the camera image assigned to the session to theone or more predefined destinations.
 5. The method of claim 4, furthercomprising: maintaining, by the content distribution subsystem, a userprofile associated with a user of the mobile device, the user profileincluding predefined distribution settings specifying the one or morepredefined destinations; wherein the distributing comprises accessingthe user profile and using the predefined distribution settings includedin the user profile to determine the one or more predefined destinationsto which to distribute the data representative of the camera imageassigned to the session.
 6. The method of claim 5, wherein thepredefined distribution settings are custom defined by the user of themobile device.
 7. The method of claim 1, further comprising: displaying,by the mobile device, an options window in the graphical user interface,the options window including a plurality of selectable options forpublishing the camera image assigned to the session; wherein thereceiving of the user input request that the data representative of thecamera image assigned to the session and stored locally by the mobiledevice be published, over the network, to the content distributionsubsystem for automatic distribution by the content distributionsubsystem to the one or more predefined destinations in accordance withthe distribution service comprises receiving a user selection, fromamong the plurality of selectable options included in the displayedoptions window, of an option to publish the camera image assigned to thesession to the distribution service.
 8. The method of claim 7, whereinthe plurality of selectable options included in the displayed optionswindow comprises: the option to publish the camera image assigned to thesession to the distribution service; and at least one of an option topublish the camera image assigned to the session to a social networksite, an option to publish the camera image assigned to the session toone or more contacts of a user of the mobile device, an option topublish the camera image assigned to the session to a web location, andan option to publish the camera image assigned to the session to alocally defined distribution list.
 9. The method of claim 1, embodied ascomputer-executable instructions on at least one non-transitorycomputer-readable medium.
 10. A system comprising: a mobile device that:captures data representative of a plurality of camera images; stores thedata representative of the plurality of camera images in a data storagefacility within the mobile device; automatically assigns a camera imageincluded in the plurality of camera images to a session based on thecamera image being captured during a particular time range; provides,for display on a display screen of the mobile device, a session specificimage manager pane together with a live camera sensor view in agraphical user interface, the session specific image manager paneincluding data representative of camera images assigned to the session;receives user input requesting that the data representative of thecamera image assigned to the session be published, over a network, forautomatic distribution in accordance with a content distributionservice; and in response to the user input, uploads the datarepresentative of the camera image assigned to the session, over thenetwork, to the content distribution service, and provides anindication, to the content distribution service over the network, thatthe data representative of the camera image assigned to the session isprovided for automatic distribution in accordance with the contentdistribution service; and a content distribution subsystemcommunicatively coupled to the mobile device by way of the network andthat: receives the data representative of the camera image assigned tothe session and the indication that the data representative of thecamera image assigned to the session is provided for automaticdistribution in accordance with the content distribution service; andautomatically distributes, in response to the receipt of the datarepresentative of the camera image assigned to the session and theindication that the data representative of the camera image assigned tothe session is provided for automatic distribution in accordance withthe distribution service, the data representative of the camera imageassigned to the session to one or more predefined destinations.
 11. Thesystem of claim 10, wherein the one or more predefined destinationscomprises a data backup storage device remote from the mobile device.12. The system of claim 10, wherein the content distribution subsystem:maintains a user profile associated with a user of the mobile device,the user profile including predefined distribution settings specifyingthe one or more predefined destinations; wherein the automaticdistributing comprises the content distribution subsystem accessing theuser profile and using the predefined distribution settings included inthe user profile to determine the one or more predefined destinations towhich to distribute the data representative of the camera image assignedto the session.
 13. The system of claim 10, wherein the session specificimage manager pane further includes a visual representation of thecamera image assigned to the session and stored in the data storagefacility within the mobile device, and a visual indication of a userinput to be provided by a user of the mobile device to cause an activeinput mode to directly toggle between the session specific image managerpane and the live camera sensor view while the live camera sensor viewand the session specific image manager pane are displayed together inthe graphical user interface.
 14. A mobile computing device comprising:a processor; a camera facility that captures a plurality of cameraimages; a data storage facility that stores data representative of theplurality of camera images; a session management facility thatautomatically assigns a camera image included in the plurality of cameraimages to a session based on the camera image being captured during aparticular time range; a user interface facility that displays a sessionspecific image manager pane together with a live camera sensor view in agraphical user interface, the session specific image manager paneincluding data representative of camera images assigned to the session;and a publishing facility that, in response to user input requestingthat the camera image assigned to the session be published, over anetwork, for automatic distribution in accordance with a contentdistribution service, uploads the data representative of the cameraimage assigned to the session, over the network, to the contentdistribution service, and provides an indication, to the contentdistribution service over the network, that the data representative ofthe camera image assigned to the session is provided for automaticdistribution to one or more predefined destinations in accordance withthe content distribution service.
 15. The mobile computing device ofclaim 14, wherein the one or more predefined destinations comprises adata backup storage device remote from the mobile computing device. 16.The mobile computing device of claim 15, wherein the one or morepredefined destinations further comprises at least one of: a computingdevice remote from the mobile computing device and associated with auser of the mobile device; and another mobile computing deviceassociated with another user.
 17. The mobile computing device of claim14, wherein the automatic distribution to the one or more predefineddestinations in accordance with the content distribution service isdefined by a user profile with the content distribution service andassociated with a user of the mobile computing device.
 18. The mobilecomputing device of claim 17, wherein the user profile includesdistribution settings custom defined by the user of the mobile deviceand that specify the one or more predefined destinations.
 19. The mobilecomputing device of claim 14, wherein the user interface facilityfurther displays an options window in the graphical user interface, theoptions window including a plurality of selectable options forpublishing the camera image assigned to the session; and an inputfacility that receives the user input requesting that the camera imageassigned to the session be published, over the network, for automaticdistribution in accordance with the content distribution service byreceiving a user selection, from among the plurality of selectableoptions included in the displayed options window, of an option topublish the camera image assigned to the session to the contentdistribution service.
 20. The mobile computing device of claim 19,wherein the plurality of selectable options included in the displayedoptions window comprises: the option to publish the camera imageassigned to the session to the content distribution service; and atleast one of an option to publish the camera image assigned to thesession to a social network site, an option to publish the camera imageassigned to the session to one or more contacts of a user of the mobiledevice, an option to publish the camera image assigned to the session toa web location, and an option to publish the camera image assigned tothe session to a locally defined distribution list.
 21. The method ofclaim 1, wherein the automatically assigning of the camera image to thesession is based on a predefined session grouping heuristic thatincludes a set of rules used to selectively assign the camera image tothe session.